Skip to content

Add Spec Trace extension to community catalog#2527

Open
Quratulain-bilal wants to merge 5 commits into
github:mainfrom
Quratulain-bilal:feat/trace-extension
Open

Add Spec Trace extension to community catalog#2527
Quratulain-bilal wants to merge 5 commits into
github:mainfrom
Quratulain-bilal:feat/trace-extension

Conversation

@Quratulain-bilal
Copy link
Copy Markdown
Contributor

@Quratulain-bilal Quratulain-bilal commented May 12, 2026

Adds Spec Trace to the community catalog — a build-time requirement → test traceability extension.

/speckit.trace.build parses spec.md for REQ-XXX tokens and the test suite for the same tokens, then writes
.specify/trace.md containing a coverage matrix. Companion commands:

  • /speckit.trace.gaps — list requirements with zero matching tests
  • /speckit.trace.orphans — list tests that do not anchor to any REQ
  • /speckit.trace.report — human-readable summary

Effect is Read+Write (because trace.build writes .specify/trace.md).

Changes

  • extensions/catalog.community.json — new "trace" entry, alphabetically placed between token-analyzer and
    v-model.
  • docs/community/extensions.md — new row added alphabetically between Spec Sync and Spec Validate. (This is
    the current location of the public community extensions table; the README table was migrated here per repo convention
    documented in .github/skills/add-community-extension/SKILL.md.)

Extension repo

Source: https://github.com/Quratulain-bilal/spec-kit-trace
Release: https://github.com/Quratulain-bilal/spec-kit-trace/releases/tag/v1.0.0
License: MIT

Verification

  • python -m json.tool extensions/catalog.community.json passes — valid JSON.
  • Row position confirmed alphabetical against neighbours in both catalog.community.json and
    docs/community/extensions.md.
  • Extension installs cleanly via specify extension add trace --from <release-url>; all four commands execute without
    errors against a project with spec.md containing REQ-XXX tokens.
  • Effect column matches actual behavior (Read+Write, since trace.build writes .specify/trace.md).

Copy link
Copy Markdown
Collaborator

@mnriem mnriem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please resolve conflicts

Note going forward adding/updating an extension please create an issue using the 'Extension Submission' template.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds the Spec Trace community extension to Spec Kit’s discovery surfaces (community catalog JSON + README table), making it easier for users to find and reference the extension for requirement→test traceability reporting.

Changes:

  • Added a new trace entry to extensions/catalog.community.json (including metadata, tags, and download URL) and bumped the catalog updated_at.
  • Added a new “Spec Trace” row to the README Community Extensions table in alphabetical order.
Show a summary per file
File Description
README.md Adds the “Spec Trace” entry to the Community Extensions table.
extensions/catalog.community.json Adds the trace extension metadata and updates updated_at.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

  • Files reviewed: 2/2 changed files
  • Comments generated: 1

Comment thread README.md Outdated
@mnriem
Copy link
Copy Markdown
Collaborator

mnriem commented May 12, 2026

Please address Copilot feedback

@Quratulain-bilal
Copy link
Copy Markdown
Contributor Author

Quratulain-bilal commented May 13, 2026

Conflicts resolved in 71300c4 clean diff now (README +1, catalog +32).

Thank you for the heads-up about the Extension Submission template I'll absolutely follow that process for all future extensions and updates going forward. Sorry for the extra work this caused; I appreciate the patience .

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

  • Files reviewed: 2/2 changed files
  • Comments generated: 1

Comment thread README.md Outdated
@mnriem
Copy link
Copy Markdown
Collaborator

mnriem commented May 13, 2026

Please address Copilot feedback

The /speckit.trace.build command writes .specify/trace.md, so the
catalog row's Effect column was wrong. Aligning with the extension's
documented behavior.
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

  • Files reviewed: 2/2 changed files
  • Comments generated: 0 new

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

  • Files reviewed: 1/1 changed files
  • Comments generated: 1

Comment thread extensions/catalog.community.json
@mnriem
Copy link
Copy Markdown
Collaborator

mnriem commented May 14, 2026

Please address Copilot feedback. Note that huge table of community extensions in the README.md has moved to docs/community/extensions.md hence why it is asking you to list it there

The public community extensions table moved from README.md to
docs/community/extensions.md per the repo convention documented in
.github/skills/add-community-extension/SKILL.md. Adding the Spec Trace
row alphabetically between Spec Sync and Spec Validate so the doc stays
in sync with the catalog entry already added.
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

  • Files reviewed: 2/2 changed files
  • Comments generated: 1

Comment thread docs/community/extensions.md
@mnriem
Copy link
Copy Markdown
Collaborator

mnriem commented May 15, 2026

Please address Copilot feedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants